WIP: Add support for deploying in containers #1035
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vitabaks
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #751
This PR introduces support for deploying cluster components inside Docker containers via
installation_method: dockervariable.Note
We do not recommend running production databases inside Docker containers. However, since some of our users prefer containers, we are adding this functionality as an option — but it will not be the default mode.
Our goal is to make this as flexible and transparent as possible, closely resembling traditional on-host package installations. For example:
systemctl start|stop patronicommandspatronictl) will internally map todocker exec -it <container> patronictl @We’re still exploring implementation details, so feedback and ideas are very welcome!